Topic
Red Hat Advanced Cluster Management for Kubernetes 2.5.2 General
Availability release images, which fix security issues and bugs.
Red Hat Product Security has rated this update as having a security impact
of Critical. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE links in the References section.
Description
Red Hat Advanced Cluster Management for Kubernetes 2.5.2 images
Red Hat Advanced Cluster Management for Kubernetes provides the
capabilities to address common challenges that administrators and site
reliability engineers face as they work across a range of public and
private cloud environments. Clusters and applications are all visible and
managed from a single console—with security policy built in.
This advisory contains the container images for Red Hat Advanced Cluster
Management for Kubernetes, which fix several bugs. See the following
Release Notes documentation, which will be updated shortly for this
release, for additional details about this release:
https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/release_notes/
Security fixes:
- moment: inefficient parsing algorithim resulting in DoS (CVE-2022-31129)
- vm2: Sandbox Escape in vm2 (CVE-2022-36067)
Bug fixes:
- Submariner Globalnet e2e tests failed on MTU between On-Prem to Public clusters (BZ# 2074547)
- OCP 4.11 - Install fails because of: pods "management-ingress-63029-5cf6789dd6-" is forbidden: unable to validate against any security context constrain (BZ# 2082254)
- subctl gather fails to gather libreswan data if CableDriver field is missing/empty in Submariner Spec (BZ# 2083659)
- Yaml editor for creating vSphere cluster moves to next line after typing (BZ# 2086883)
- Submariner addon status doesn't track all deployment failures (BZ# 2090311)
- Unable to deploy Hypershift operator on MCE hub using ManagedClusterAddOn without including s3 secret (BZ# 2091170)
- After switching to ACM 2.5 the managed clusters log "unable to create ClusterClaim" errors (BZ# 2095481)
- Enforce failed and report the violation after modified memory value in limitrange policy (BZ# 2100036)
- Creating an application fails with "This application has no subscription match selector (spec.selector.matchExpressions)" (BZ# 2101577)
- Inconsistent cluster resource statuses between "All Subscription" topology and individual topologies (BZ# 2102273)
- managed cluster is in "unknown" state for 120 mins after OADP restore
- RHACM 2.5.2 images (BZ# 2104553)
- Subscription UI does not allow binding to label with empty value (BZ# 2104961)
- Upgrade to 2.5.1 from 2.5.0 fails due to missing Subscription CRD (BZ# 2106069)
- Region information is not available for Azure cloud in managedcluster CR (BZ# 2107134)
- cluster uninstall log points to incorrect container name (BZ# 2107359)
- ACM shows wrong path for Argo CD applicationset git generator (BZ# 2107885)
- Single node checkbox not visible for 4.11 images (BZ# 2109134)
- Unable to deploy hypershift cluster when enabling validate-cluster-security (BZ# 2109544)
- Deletion of Application (including app related resources) from the console fails to delete PlacementRule for the application (BZ# 20110026)
- After the creation by a policy of job or deployment (in case the object is missing)ACM is trying to add new containers instead of updating (BZ# 2117728)
- pods in CrashLoopBackoff on 3.11 managed cluster (BZ# 2122292)
- ArgoCD and AppSet Applications do not deploy to local-cluster (BZ# 2124707)
Vulmon